-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Add roadmap for 2026 #7778
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add roadmap for 2026 #7778
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
UlisesGascon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this is in draft, feel free to ignore if early feedback isn't needed yet! 🙂
|
@UlisesGascon see #7780 for more changes and provide feedback! |
|
thanks @bjohansebas I will focus on #7780 👍 |
Co-authored-by: Ulises Gascón <ulisesgascongonzalez@gmail.com>
|
Thanks for co-reviewing @UlisesGascon will have a look tomorrow! |
…7780) * docs(blog): update roadmap for 2026 with CSS Modules support details * docs(blog): add details on universal target support * docs(blog): integrate HTML module support as entry points without plugins * docs(blog): expand TypeScript support by eliminating loader requirements * docs(blog): add support for Deno and Bun * docs(blog): enhance support for Node, Deno, and Bun with a runtime-agnostic architecture * docs(blog): simplify asset minimization by consolidating multiple plugins into a single minimizer-webpack-plugin * docs(blog): update section headers * docs(blog): update roadmap details for universal target and ESM output progress * docs(blog): enhance design and visual identity with new assets for projects and merchandise * docs(blog): enhance documentation accuracy by enabling auto-generation from webpack types and schemas * docs(blog): add section on community outreach and engagement to enhance developer connections * docs(blog): streamline webpack's development experience with improved dev tooling and CLI enhancements * docs(blog): add GSoC mentorship section to highlight student engagement and open source sustainability * docs(blog): add Multithreading API section to outline performance improvements and ongoing design discussions * docs(blog): add section on donations and sponsorships to emphasize funding importance for webpack maintenance * docs(blog): add section on lazy barrel optimization to explore performance improvements inspired by Rspack * docs(blog): update roadmap for Webpack 6 preparation, highlighting core improvements, testing priorities, and performance benchmarks * docs(blog): refine language and formatting in roadmap for 2026, enhancing clarity and readability * docs(blog): enhance runtime compatibility section, detailing webpack's support for alternative JavaScript runtimes and intelligent module handling * docs(blog): add links to discussions on experimental CSS support and universal target for cross-runtime compatibility * docs(blog): move section * docs(blog): update roadmap for 2026, enhancing clarity and excitement about upcoming features * chore: revise text Co-authored-by: Sebastian Beltran <bjohansebas@gmail.com> --------- Co-authored-by: Even Stensberg <evenstensberg@gmail.com>
|
@copilot review this pr |
|
@evenstensberg I've opened a new pull request, #7802, to work on those changes. Once the pull request is ready, I'll request review from you. |
|
CI check is failing for one invalid link, can you check? |
|
PTAL |
alexander-akait
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bjohansebas Can you look at this too? Thanks
bjohansebas
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, nothing blocking
Summary
Adds roadmap for 2026
What kind of change does this PR introduce?
new docs
Did you add tests for your changes?
N/A
Does this PR introduce a breaking change?
No
If relevant, what needs to be documented once your changes are merged or what have you already documented?
N/A